GM Homonoia wrote:Arkady Sadik wrote:GM Homonoia wrote:However: Spamming a button is never a feature and is never guaranteed to work. Spamming the warp button has never been a 100% guarantee escape and it was definitely not designed to be so. In fact, spamming any button can cause client side lag. It may help you get the perfect timing right, it is just as likely to drown the client or your connection and make things worse.
Well, one thing that is definitely true since Crucible is that the lag caused by "spamming" (I hit the warp button twice a second tops for pod escape, worked very well in the past) is that the client lags a lot more on quite a few situations. This is difficult to bug report, as it's not a single bug you can easily reproduce, but it feels a lot more laggy. And that would indicate a software problem that should be fixed, regardless of whether the "pod escape" is an intended feature or not.
That, unfortunately, is something I cannot really go into as I simply lack the skills (not a programmer or QA person) to delve into this. I realize that bug reporting this isn't easy, but it is still the best way to get programmers to notice.
What I can promise you is that I will keep an eye out for this (both as a game master and as a player) and will pass anything I find up the chain.
okay, after pondering for a few moments on your view i have come to the following conclusion.
Lag due to spamming may infact be possible but looking at the logs it was between 5 and 9 seconds after lossing the ship and being in a pod and being unable to warp the whole time, and again looking at the logs it states the reason as being already in warp. im sure a pod can align and warp in less than 5 seconds even with lag. This indicated a programming/software issue to me. state change problems?
another thing, i had no clientside lag at the time of the incident, you only have my word for this though as i wasnt recording the fight due to 2 scorps decloaking and me thinking it was pointless :D
on a side note:
i had had the issue with session change simply not expireing before since cruicible, ive been sat on a gate for 3 minutes not being able to jump because my session change didn't expire, maybe another state change problem in the client? only relogging fixed the problem.